-
Notifications
You must be signed in to change notification settings - Fork 421
fix(batch): Correctly handle child_exceptions
being None
#1205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(batch): Correctly handle child_exceptions
being None
#1205
Conversation
Change: - Allow for child_exceptions being none in format_exceptions fixes aws-powertools#1203
I can’t stress this enough @michaelbrewer, In an effort to prevent you from wasting time, you should wait for issues to prioritised, this won't be merged for a long time until we're ready to add new features. |
Note that this bug will cause a crash when there are no child exceptions. |
Codecov Report
@@ Coverage Diff @@
## develop #1205 +/- ##
========================================
Coverage 99.88% 99.88%
========================================
Files 119 119
Lines 5423 5423
Branches 618 618
========================================
Hits 5417 5417
Misses 2 2
Partials 4 4
Continue to review full report at Codecov.
|
child_exceptions
being None
Issue number:
Summary
Following code raises a runtime error:
Changes
Change:
child_exceptions
being None informat_exceptions
which is used when the error is printed.User experience
Following code would not raise any errors
Other solutions considered
child_exceptions
is not possible asmsg
has a default value.child_exceptions
to()
would generate a typing error with MyPychild_exceptions
to[]
would make the default argument mutablemsg
andchild_exceptions
to be required would be a breaking changeself. child_exceptions
is[]
when None would also change the type ofchild_exceptions
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.